Repository navigation
web: embed-followups - #871
Conversation
PM note: how this PR will be handledWhat it is for: web: embed-followups Rules that apply: touches CI or workflows; changes agent rules or guides. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Waiting for the maintainer What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches CI or workflows; changes agent rules or guides. Reviews at the current commit (
6 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/395#issuecomment-6452386864 (1 finding answered) Updated 2026-10-27 23:01 UTC by the PM. This comment is edited in place. |
Main keeps its web JS tests in web/tests/; the embed test sat in a second directory. CI still runs it in its own step: it needs no built web.js, unlike scripts/test-web-text-input.sh. Agent-Team: linux Worker: claude Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Main's fizzy.js imports TextInput from web.js; the stand-in lacked it after the merge. Agent-Team: linux Worker: claude Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Agent-Team: linux Worker: codex
Part of fizzyedit/work#361
Credit: this follows Michael Belousov's #835 (embeddable Fizzy, several copies on one page) and his issue #829; the fixes here close the gaps found in it. (Added by the PM for work#361's Done.)
Rework: work#547
Goal
Part of fizzyedit/work#361. Support multiple embedded Fizzy copies with shared compilation and isolated keyboard/fullscreen handling. This round addresses the newest PR #871 ruling on linux/codex F1.
What changed and why
The existing scripts/test-web-text-input.sh now runs the embed test after the hidden-input test under Node, and offers --embed-only for its build-independent fixture. CI invokes that script from its existing web compilation step; the separate embed-test step is removed. All other PR behavior stays as supplied.
How it was verified
The embed-only runner passes without built web assets; after building web, the default runner reports both text-input: ok and embed.test: ok. Before this change the existing runner never executed the embed check. The two-copies regression test covers shared compilation, key isolation and per-copy fullscreen. Prior negative-test evidence against main is recorded in the supplied review thread; it was not repeated this round. Format, lint, native build, unit, integration, web build, check-web and SDK-version gates pass; counts and cached-result qualifications are in the harness gate report.
Not done / follow-ups
No browser interaction was changed or checked this round. Optional earlier findings remain follow-ups per the ruling. Publishing and the numbered FIXES comment are left to the harness; maintainer approval remains outstanding.
Changes (64 files, +355/-1647)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)